Skip to content

Conversation

@maheshwarip
Copy link
Contributor

No description provided.

@maheshwarip maheshwarip requested review from a team, elithrar and harshil1712 as code owners March 30, 2025 21:40
@github-actions github-actions bot added size/s product:queues Cloudflare Queues: https://developers.cloudflare.com/queues labels Mar 30, 2025
@hyperlint-ai
Copy link
Contributor

hyperlint-ai bot commented Mar 30, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Updated the queues REST API limits and made clarifications regarding message retention and API rate limits.

  • Clarified that multiple concurrent pull-based consumers can be authenticated against a single queue without shared rate limits.
  • Updated message retention period from 14 days to 4 days by default, with configuration options available.
  • Adjusted wording to recommend grouping acknowledgements to reduce API calls instead of avoiding rate limits.

Modified Files

  • src/content/docs/queues/configuration/pull-consumers.mdx
  • src/content/docs/queues/platform/limits.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

@maheshwarip maheshwarip marked this pull request as draft March 30, 2025 21:40
@maheshwarip maheshwarip changed the title (WIP) Updating queues REST API limits Updating queues REST API limits Apr 15, 2025
@maheshwarip maheshwarip changed the title Updating queues REST API limits Updating queues pull consumer limits Apr 15, 2025
@maheshwarip maheshwarip marked this pull request as ready for review April 15, 2025 20:49
@maheshwarip maheshwarip requested a review from a team as a code owner April 15, 2025 20:49
@maheshwarip maheshwarip enabled auto-merge (squash) April 16, 2025 17:30

To setup a new queue with a pull based consumer using [Wrangler](/workers/wrangler/), run:
```bash title="Create a queue with a pull based consumer"
$ npx wrangler queues create my-queue
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can also configure a pull consumer using the [REST API](/api/resources/queues/subresources/consumers/methods/create/) or the Queues dashboard.

Once configured, you can pull messages from the queue using any HTTP client. You'll need a [Cloudflare API Token](/fundamentals/api/get-started/create-token/) with `queues_read` and `queues_write` permissions. For example:
```bash title="Pull messages from a queue"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May want to move this to our APIRequest component

@maheshwarip maheshwarip merged commit fe21273 into production Apr 16, 2025
12 checks passed
@maheshwarip maheshwarip deleted the pm-queues-http-pull branch April 16, 2025 19:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge-yet product:queues Cloudflare Queues: https://developers.cloudflare.com/queues size/s

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants